API

Procurement APIs

POST procurement/sop-processes

Creates a new S&OP (sales and operation planning) processes

HTTP method POST
URI https://api.rambase.net/procurement/sop-processes
Supported formats Xml, Html, Json (ex. $format=json)
Successful HTTP status code 201
API resource identifier 3384, version 16

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<SOPProcess>
2
     <Name
Name

Required/mandatory field

Name of S&OP (Sales and operation planning) process

Minimum value: 1

>
{String}</Name>
3
     <Description
Description

Description of S&OP (Sales and operations planning) process

This field is optional.

>
{String}</Description>
4
     <Granularity
Granularity

Granularity used to present the different plans in the S&OP process. Week or month.

Applicable domain values can be found here

Default value: WEEK

This field is optional.

>
{String}</Granularity>
5
     <Location
Location

This field is optional.

>
6
          <LocationId
LocationId

Location identifier

Minimum value: 10000

This field is optional.

>
{Integer}</LocationId>
7
     </Location>
8
     <DemandForecast
DemandForecast

This field is optional.

>
9
          <SalesForecastSource
SalesForecastSource

The source to use from the sales forecast

Applicable domain values can be found here

This field is optional.

>
{Integer}</SalesForecastSource>
10
          <IncludeSalesBacklog
IncludeSalesBacklog

If sales backlog is included, everything from the backlog is added to the demand forecast. Note that backlog from products sales forecasted by customers (through the sales forecast source), will not be included.

Default value: False

This field is optional.

>
{Boolean}</IncludeSalesBacklog>
11
          <SalesBacklogExclusion
SalesBacklogExclusion

This field will only have any effect if the “include sales backlog” option is set.
The default (Exclude nothing) is that sales backlog for the same customer and product that exist in the sales forecast will be excluded from the sales and operation planning. This field is used to fine tune what will be included or not from the sales backlog.

Applicable domain values can be found here

This field is optional.

>
{Integer}</SalesBacklogExclusion>
12
          <IncludeReOrderPointForPurchase
IncludeReOrderPointForPurchase

If products which are purchased have specified re-order point for the location used in the S&OP process, the re-order point will be added as a demand. This will then be included in the gross quantity of the purchase requirements. Note that this also includes products with product structures manufactured externally.

Default value: True

This field is optional.

>
{Boolean}</IncludeReOrderPointForPurchase>
13
          <IncludeReOrderPointForProduction
IncludeReOrderPointForProduction

If products which are manufactured have specified re-order point quantity for the location used in the S&OP process, the re-order point quantity will be added as a demand. This will then be included in the gross quantity of the production requirements. Note that this does not includes products with product structures manufactured externally.

Default value: True

This field is optional.

>
{Boolean}</IncludeReOrderPointForProduction>
14
          <MinimumProbabilityPercent
MinimumProbabilityPercent

Minimum probability in percentage to include from the sales forecast

Minimum value: 0

Maximum value: 100

Default value: 0

This field is optional.

>
{Decimal}</MinimumProbabilityPercent>
15
          <MaximumProbabilityPercent
MaximumProbabilityPercent

Maximum probability in percentage to include from the sales forecast

Minimum value: 0

Maximum value: 100

Default value: 100

This field is optional.

>
{Decimal}</MaximumProbabilityPercent>
16
     </DemandForecast>
17
     <ProductionRequirements
ProductionRequirements

This field is optional.

>
18
          <TreatProductionWorkOrdersAsStock
TreatProductionWorkOrdersAsStock

By enabling this, existing, but not completed, production work orders will be treated as stock. Any production work orders can be used to net off production requirements. By not enabling this, you might end up with creating new production work orders instead off replanning already existing production work orders.

Default value: False

This field is optional.

>
{Boolean}</TreatProductionWorkOrdersAsStock>
19
     </ProductionRequirements>
20
     <PurchaseRequirements
PurchaseRequirements

This field is optional.

>
21
          <TreatSupplierBacklogAsStock
TreatSupplierBacklogAsStock

By enabling this all purchase orders and purchase order responses will be treated as stock. Any purchase orders and purchase order responses confirmed in the future (ex. in two months) is available from today and can be used to net off purchase requirements. By not enabling this, you might end up with purchasing products that could instead be aquired by requesting change of delivery date on existing supplier backlog.

Default value: False

This field is optional.

>
{Boolean}</TreatSupplierBacklogAsStock>
22
          <RequireMaterialsFromAllProductionWorkOrders
RequireMaterialsFromAllProductionWorkOrders

By enabling this option, materials from ALL ongoing- and planned production work orders are included as gross purchase requirements. This means that you might get purchase requirements for materials belonging to production work orders not related to the production requirement plan.

If this option is disabled, only materials needed to fulfill the production requirements are included as gross purchase requirements. Note that even if this option is disabled you will still get purchase requirements for materials in ongoing- and planned production work orders consumed by (net off) the production requirements.

Default value: False

This field is optional.

>
{Boolean}</RequireMaterialsFromAllProductionWorkOrders>
23
     </PurchaseRequirements>
24
     <PurchaseOrderSuggestions
PurchaseOrderSuggestions

This field is optional.

>
25
          <RequestedDeliveryDay
RequestedDeliveryDay

Preferred day of delivery. Used to consolidate purchase order suggestions. Default is all days.

Applicable domain values can be found here

Minimum value: 0

Maximum value: 7

Default value: 0

This field is optional.

>
{Integer}</RequestedDeliveryDay>
26
     </PurchaseOrderSuggestions>
27
</SOPProcess>
1
{
2
     "sOPProcess": {
3
          "name
Name

Required/mandatory field

Name of S&OP (Sales and operation planning) process

Minimum value: 1

":
"{String}",
4
          "description
Description

Description of S&OP (Sales and operations planning) process

This field is optional.

":
"{String}",
5
          "granularity
Granularity

Granularity used to present the different plans in the S&OP process. Week or month.

Applicable domain values can be found here

Default value: WEEK

This field is optional.

":
"{String}",
6
          "location
Location

This field is optional.

":
{
7
               "locationId
LocationId

Location identifier

Minimum value: 10000

This field is optional.

":
"{Integer}"
8
          },
9
          "demandForecast
DemandForecast

This field is optional.

":
{
10
               "salesForecastSource
SalesForecastSource

The source to use from the sales forecast

Applicable domain values can be found here

This field is optional.

":
"{Integer}",
11
               "includeSalesBacklog
IncludeSalesBacklog

If sales backlog is included, everything from the backlog is added to the demand forecast. Note that backlog from products sales forecasted by customers (through the sales forecast source), will not be included.

Default value: False

This field is optional.

":
"{Boolean}",
12
               "salesBacklogExclusion
SalesBacklogExclusion

This field will only have any effect if the “include sales backlog” option is set.
The default (Exclude nothing) is that sales backlog for the same customer and product that exist in the sales forecast will be excluded from the sales and operation planning. This field is used to fine tune what will be included or not from the sales backlog.

Applicable domain values can be found here

This field is optional.

":
"{Integer}",
13
               "includeReOrderPointForPurchase
IncludeReOrderPointForPurchase

If products which are purchased have specified re-order point for the location used in the S&OP process, the re-order point will be added as a demand. This will then be included in the gross quantity of the purchase requirements. Note that this also includes products with product structures manufactured externally.

Default value: True

This field is optional.

":
"{Boolean}",
14
               "includeReOrderPointForProduction
IncludeReOrderPointForProduction

If products which are manufactured have specified re-order point quantity for the location used in the S&OP process, the re-order point quantity will be added as a demand. This will then be included in the gross quantity of the production requirements. Note that this does not includes products with product structures manufactured externally.

Default value: True

This field is optional.

":
"{Boolean}",
15
               "minimumProbabilityPercent
MinimumProbabilityPercent

Minimum probability in percentage to include from the sales forecast

Minimum value: 0

Maximum value: 100

Default value: 0

This field is optional.

":
"{Decimal}",
16
               "maximumProbabilityPercent
MaximumProbabilityPercent

Maximum probability in percentage to include from the sales forecast

Minimum value: 0

Maximum value: 100

Default value: 100

This field is optional.

":
"{Decimal}"
17
          },
18
          "productionRequirements
ProductionRequirements

This field is optional.

":
{
19
               "treatProductionWorkOrdersAsStock
TreatProductionWorkOrdersAsStock

By enabling this, existing, but not completed, production work orders will be treated as stock. Any production work orders can be used to net off production requirements. By not enabling this, you might end up with creating new production work orders instead off replanning already existing production work orders.

Default value: False

This field is optional.

":
"{Boolean}"
20
          },
21
          "purchaseRequirements
PurchaseRequirements

This field is optional.

":
{
22
               "treatSupplierBacklogAsStock
TreatSupplierBacklogAsStock

By enabling this all purchase orders and purchase order responses will be treated as stock. Any purchase orders and purchase order responses confirmed in the future (ex. in two months) is available from today and can be used to net off purchase requirements. By not enabling this, you might end up with purchasing products that could instead be aquired by requesting change of delivery date on existing supplier backlog.

Default value: False

This field is optional.

":
"{Boolean}",
23
               "requireMaterialsFromAllProductionWorkOrders
RequireMaterialsFromAllProductionWorkOrders

By enabling this option, materials from ALL ongoing- and planned production work orders are included as gross purchase requirements. This means that you might get purchase requirements for materials belonging to production work orders not related to the production requirement plan.

If this option is disabled, only materials needed to fulfill the production requirements are included as gross purchase requirements. Note that even if this option is disabled you will still get purchase requirements for materials in ongoing- and planned production work orders consumed by (net off) the production requirements.

Default value: False

This field is optional.

":
"{Boolean}"
24
          },
25
          "purchaseOrderSuggestions
PurchaseOrderSuggestions

This field is optional.

":
{
26
               "requestedDeliveryDay
RequestedDeliveryDay

Preferred day of delivery. Used to consolidate purchase order suggestions. Default is all days.

Applicable domain values can be found here

Minimum value: 0

Maximum value: 7

Default value: 0

This field is optional.

":
"{Integer}"
27
          }
28
     }
29
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<SOPProcess>
2
     <SOPProcessId
SOPProcessId

S&OP (sales and operation planning) process identifier

>
{Integer}</SOPProcessId>
3
     <Status
Status

Status of S&OP (sales and production planning) process

Possible domain values can be found here

>
{Integer}</Status>
4
     <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
5
     <Name
Name

Name of S&OP (Sales and operation planning) process

>
{String}</Name>
6
     <Description
Description

Description of S&OP (Sales and operations planning) process

>
{String}</Description>
7
     <Granularity
Granularity

Granularity used to present the different plans in the S&OP process. Week or month.

Possible domain values can be found here

>
{String}</Granularity>
8
     <Location>
9
          <LocationId
LocationId

Location identifier

>
{Integer}</LocationId>
10
          <ShortName
ShortName

Unique abbreviation/short name of the location

>
{String}</ShortName>
11
          <Name
Name

Name of warehouse location

>
{String}</Name>
12
          <LocationLink
LocationLink

Location reference

>
{String}</LocationLink>
13
     </Location>
14
     <LatestBatchJob>
15
          <BatchJobId
BatchJobId

Batch job identifier

>
{Integer}</BatchJobId>
16
          <Status
Status

Status of batch job

Possible domain values can be found here

>
{Integer}</Status>
17
          <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
18
          <StartedAt
StartedAt

Date and time of the batch job start

>
{Datetime}</StartedAt>
19
          <FinishedAt
FinishedAt

Enddate and endtime of the batch job

>
{Datetime}</FinishedAt>
20
          <BatchJobLink
BatchJobLink

Batch job reference

>
{String}</BatchJobLink>
21
     </LatestBatchJob>
22
     <DemandForecast>
23
          <UpdatedAt
UpdatedAt

Date and time demand forecasts were created

>
{Datetime}</UpdatedAt>
24
          <IncludeSalesBacklog
IncludeSalesBacklog

If sales backlog is included, everything from the backlog is added to the demand forecast. Note that backlog from products sales forecasted by customers (through the sales forecast source), will not be included.

>
{Boolean}</IncludeSalesBacklog>
25
          <SalesBacklogExclusion
SalesBacklogExclusion

This field will only have any effect if the “include sales backlog” option is set.
The default (Exclude nothing) is that sales backlog for the same customer and product that exist in the sales forecast will be excluded from the sales and operation planning. This field is used to fine tune what will be included or not from the sales backlog.

Possible domain values can be found here

>
{Integer}</SalesBacklogExclusion>
26
          <IncludeReOrderPointForPurchase
IncludeReOrderPointForPurchase

If products which are purchased have specified re-order point for the location used in the S&OP process, the re-order point will be added as a demand. This will then be included in the gross quantity of the purchase requirements. Note that this also includes products with product structures manufactured externally.

>
{Boolean}</IncludeReOrderPointForPurchase>
27
          <IncludeReOrderPointForProduction
IncludeReOrderPointForProduction

If products which are manufactured have specified re-order point quantity for the location used in the S&OP process, the re-order point quantity will be added as a demand. This will then be included in the gross quantity of the production requirements. Note that this does not includes products with product structures manufactured externally.

>
{Boolean}</IncludeReOrderPointForProduction>
28
          <SalesForecastSource
SalesForecastSource

The source to use from the sales forecast

Possible domain values can be found here

>
{Integer}</SalesForecastSource>
29
          <MinimumProbabilityPercent
MinimumProbabilityPercent

Minimum probability in percentage to include from the sales forecast

>
{Decimal}</MinimumProbabilityPercent>
30
          <MaximumProbabilityPercent
MaximumProbabilityPercent

Maximum probability in percentage to include from the sales forecast

>
{Decimal}</MaximumProbabilityPercent>
31
     </DemandForecast>
32
     <ProductionRequirements>
33
          <UpdatedAt
UpdatedAt

Date and time production requirements were updated for this S&OP process

>
{Datetime}</UpdatedAt>
34
          <TreatProductionWorkOrdersAsStock
TreatProductionWorkOrdersAsStock

By enabling this, existing, but not completed, production work orders will be treated as stock. Any production work orders can be used to net off production requirements. By not enabling this, you might end up with creating new production work orders instead off replanning already existing production work orders.

>
{Boolean}</TreatProductionWorkOrdersAsStock>
35
     </ProductionRequirements>
36
     <PurchaseRequirements>
37
          <UpdatedAt
UpdatedAt

Date and time purchase requirements was updated in this S&OP process

>
{Datetime}</UpdatedAt>
38
          <TreatSupplierBacklogAsStock
TreatSupplierBacklogAsStock

By enabling this all purchase orders and purchase order responses will be treated as stock. Any purchase orders and purchase order responses confirmed in the future (ex. in two months) is available from today and can be used to net off purchase requirements. By not enabling this, you might end up with purchasing products that could instead be aquired by requesting change of delivery date on existing supplier backlog.

>
{Boolean}</TreatSupplierBacklogAsStock>
39
          <RequireMaterialsFromAllProductionWorkOrders
RequireMaterialsFromAllProductionWorkOrders

By enabling this option, materials from ALL ongoing- and planned production work orders are included as gross purchase requirements. This means that you might get purchase requirements for materials belonging to production work orders not related to the production requirement plan.

If this option is disabled, only materials needed to fulfill the production requirements are included as gross purchase requirements. Note that even if this option is disabled you will still get purchase requirements for materials in ongoing- and planned production work orders consumed by (net off) the production requirements.

>
{Boolean}</RequireMaterialsFromAllProductionWorkOrders>
40
     </PurchaseRequirements>
41
     <PurchaseOrderSuggestions>
42
          <UpdatedAt
UpdatedAt

Date and time purchase order suggestions were updated for this S&OP process

>
{Datetime}</UpdatedAt>
43
          <RequestedDeliveryDay
RequestedDeliveryDay

Preferred day of delivery. Used to consolidate purchase order suggestions. Default is all days.

Possible domain values can be found here

>
{Integer}</RequestedDeliveryDay>
44
     </PurchaseOrderSuggestions>
45
</SOPProcess>
1
{
2
     "sOPProcess": {
3
          "sOPProcessId
SOPProcessId

S&OP (sales and operation planning) process identifier

":
"{Integer}",
4
          "status
Status

Status of S&OP (sales and production planning) process

Possible domain values can be found here

":
"{Integer}",
5
          "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
6
          "name
Name

Name of S&OP (Sales and operation planning) process

":
"{String}",
7
          "description
Description

Description of S&OP (Sales and operations planning) process

":
"{String}",
8
          "granularity
Granularity

Granularity used to present the different plans in the S&OP process. Week or month.

Possible domain values can be found here

":
"{String}",
9
          "location": {
10
               "locationId
LocationId

Location identifier

":
"{Integer}",
11
               "shortName
ShortName

Unique abbreviation/short name of the location

":
"{String}",
12
               "name
Name

Name of warehouse location

":
"{String}",
13
               "locationLink
LocationLink

Location reference

":
"{String}"
14
          },
15
          "latestBatchJob": {
16
               "batchJobId
BatchJobId

Batch job identifier

":
"{Integer}",
17
               "status
Status

Status of batch job

Possible domain values can be found here

":
"{Integer}",
18
               "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
19
               "startedAt
StartedAt

Date and time of the batch job start

":
"{Datetime}",
20
               "finishedAt
FinishedAt

Enddate and endtime of the batch job

":
"{Datetime}",
21
               "batchJobLink
BatchJobLink

Batch job reference

":
"{String}"
22
          },
23
          "demandForecast": {
24
               "updatedAt
UpdatedAt

Date and time demand forecasts were created

":
"{Datetime}",
25
               "includeSalesBacklog
IncludeSalesBacklog

If sales backlog is included, everything from the backlog is added to the demand forecast. Note that backlog from products sales forecasted by customers (through the sales forecast source), will not be included.

":
"{Boolean}",
26
               "salesBacklogExclusion
SalesBacklogExclusion

This field will only have any effect if the “include sales backlog” option is set.
The default (Exclude nothing) is that sales backlog for the same customer and product that exist in the sales forecast will be excluded from the sales and operation planning. This field is used to fine tune what will be included or not from the sales backlog.

Possible domain values can be found here

":
"{Integer}",
27
               "includeReOrderPointForPurchase
IncludeReOrderPointForPurchase

If products which are purchased have specified re-order point for the location used in the S&OP process, the re-order point will be added as a demand. This will then be included in the gross quantity of the purchase requirements. Note that this also includes products with product structures manufactured externally.

":
"{Boolean}",
28
               "includeReOrderPointForProduction
IncludeReOrderPointForProduction

If products which are manufactured have specified re-order point quantity for the location used in the S&OP process, the re-order point quantity will be added as a demand. This will then be included in the gross quantity of the production requirements. Note that this does not includes products with product structures manufactured externally.

":
"{Boolean}",
29
               "salesForecastSource
SalesForecastSource

The source to use from the sales forecast

Possible domain values can be found here

":
"{Integer}",
30
               "minimumProbabilityPercent
MinimumProbabilityPercent

Minimum probability in percentage to include from the sales forecast

":
"{Decimal}",
31
               "maximumProbabilityPercent
MaximumProbabilityPercent

Maximum probability in percentage to include from the sales forecast

":
"{Decimal}"
32
          },
33
          "productionRequirements": {
34
               "updatedAt
UpdatedAt

Date and time production requirements were updated for this S&OP process

":
"{Datetime}",
35
               "treatProductionWorkOrdersAsStock
TreatProductionWorkOrdersAsStock

By enabling this, existing, but not completed, production work orders will be treated as stock. Any production work orders can be used to net off production requirements. By not enabling this, you might end up with creating new production work orders instead off replanning already existing production work orders.

":
"{Boolean}"
36
          },
37
          "purchaseRequirements": {
38
               "updatedAt
UpdatedAt

Date and time purchase requirements was updated in this S&OP process

":
"{Datetime}",
39
               "treatSupplierBacklogAsStock
TreatSupplierBacklogAsStock

By enabling this all purchase orders and purchase order responses will be treated as stock. Any purchase orders and purchase order responses confirmed in the future (ex. in two months) is available from today and can be used to net off purchase requirements. By not enabling this, you might end up with purchasing products that could instead be aquired by requesting change of delivery date on existing supplier backlog.

":
"{Boolean}",
40
               "requireMaterialsFromAllProductionWorkOrders
RequireMaterialsFromAllProductionWorkOrders

By enabling this option, materials from ALL ongoing- and planned production work orders are included as gross purchase requirements. This means that you might get purchase requirements for materials belonging to production work orders not related to the production requirement plan.

If this option is disabled, only materials needed to fulfill the production requirements are included as gross purchase requirements. Note that even if this option is disabled you will still get purchase requirements for materials in ongoing- and planned production work orders consumed by (net off) the production requirements.

":
"{Boolean}"
41
          },
42
          "purchaseOrderSuggestions": {
43
               "updatedAt
UpdatedAt

Date and time purchase order suggestions were updated for this S&OP process

":
"{Datetime}",
44
               "requestedDeliveryDay
RequestedDeliveryDay

Preferred day of delivery. Used to consolidate purchase order suggestions. Default is all days.

Possible domain values can be found here

":
"{Integer}"
45
          }
46
     }
47
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 100199 HTTP 404 Location not found